-- Network Working Group M. Dubuc
-- Request for Comments: 4327 T. Nadeau
-- Category: Standards Track Cisco Systems
-- J. Lang
-- Sonos, Inc.
-- E. McGinnis
-- Hammerhead Systems
-- January 2006-- Link Management Protocol (LMP) Management Information Base (MIB)LMP-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,NOTIFICATION-TYPE,transmission,Unsigned32,Counter32,TimeTicksFROM SNMPv2-SMI -- [RFC2578]MODULE-COMPLIANCE,OBJECT-GROUP,NOTIFICATION-GROUPFROM SNMPv2-CONF -- [RFC2580]TEXTUAL-CONVENTION,TruthValue,RowStatus,StorageType,TimeStampFROM SNMPv2-TC -- [RFC2579]InterfaceIndexOrZero, ifIndex
FROM IF-MIB -- [RFC2863]InetAddressType,InetAddressFROM INET-ADDRESS-MIB -- [RFC4001]teLinkRemoteIpAddr, teLinkIncomingIfId,TeLinkEncodingTypeFROM TE-LINK-STD-MIB;-- [RFC4220]lmpMIB MODULE-IDENTITYLAST-UPDATED"200601110000Z"-- 11 January 2006ORGANIZATION"Common Control and Measurement Protocols (CCAMP)
Working Group"CONTACT-INFO" Martin Dubuc
Email: dubuc.consulting@sympatico.ca
Thomas D. Nadeau
Email: tnadeau@cisco.com
Jonathan P. Lang
Email: jplang@ieee.org
Evan McGinnis
Email: emcginnis@hammerheadsystems.com"DESCRIPTION"Copyright (C) 2006 The Internet Society. This version of
the MIB module is part of RFC 4327; see the RFC itself
for full legal notices.
This MIB module contains managed object definitions for
the Link Management Protocol (LMP) as
defined in 'Link Management Protocol'."-- Revision history.REVISION"200601110000Z"-- 11 January 2006DESCRIPTION"Initial version published as RFC 4327"::={ transmission 227}-- Textual ConventionsLmpInterval::=TEXTUAL-CONVENTIONDISPLAY-HINT"d"STATUScurrentDESCRIPTION"The interval delay in milliseconds."SYNTAXUnsigned32(1..65535)LmpRetransmitInterval::=TEXTUAL-CONVENTION
DISPLAY-HINT"d"STATUScurrentDESCRIPTION"The retransmission interval delay in milliseconds."SYNTAXUnsigned32(1..4294967295)LmpNodeId::=TEXTUAL-CONVENTIONDISPLAY-HINT"1d.1d.1d.1d"STATUScurrentDESCRIPTION"Represents a Node ID in network byte order. Node ID is an
address of type IPv4."REFERENCE"Section 1.1 of Link Management Protocol, RFC 4204"SYNTAXOCTETSTRING(SIZE(4))-- Top level components of this MIB-- NotificationslmpNotifications OBJECTIDENTIFIER::={ lmpMIB 0}-- Tables, ScalarslmpObjects OBJECTIDENTIFIER::={ lmpMIB 1}-- ConformancelmpConformance OBJECTIDENTIFIER::={ lmpMIB 2}lmpAdminStatus OBJECT-TYPESYNTAXINTEGER{ up(1), down(2)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The desired operational status of LMP on the node.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."DEFVAL{ up }::={ lmpObjects 1}lmpOperStatus OBJECT-TYPESYNTAXINTEGER{ up(1), down(2)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The actual operational status of LMP on the node."::={ lmpObjects 2}-- LMP Neighbor TablelmpNbrTable OBJECT-TYPESYNTAXSEQUENCEOF LmpNbrEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies the neighbor node(s) to which control
channels may be established."::={ lmpObjects 3}lmpNbrEntry OBJECT-TYPESYNTAX LmpNbrEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table is created by a LMP-enabled device for
every pair of nodes that can establish control channels."INDEX{ lmpNbrNodeId }::={ lmpNbrTable 1}
LmpNbrEntry ::=SEQUENCE{
lmpNbrNodeId LmpNodeId,
lmpNbrRetransmitInterval LmpRetransmitInterval,
lmpNbrRetryLimit Unsigned32,
lmpNbrRetransmitDelta Unsigned32,
lmpNbrAdminStatus INTEGER,
lmpNbrOperStatus INTEGER,
lmpNbrRowStatus RowStatus,
lmpNbrStorageType StorageType}lmpNbrNodeId OBJECT-TYPESYNTAXLmpNodeIdMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This is a unique index for an entry in the LmpNbrTable.
This value represents the remote Node ID."::={ lmpNbrEntry 1}lmpNbrRetransmitInterval OBJECT-TYPESYNTAXLmpRetransmitIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the initial retransmission interval that
is used for the retransmission of messages that require
acknowledgement. This object along with lmpNbrRetryLimit is
used to implement congestion-handling mechanism as defined in
Section 10 of the Link Management Protocol specification,
which is based on RFC 2914."REFERENCE"Link Management Protocol, RFC 4204.
Congestion Control Principles, RFC 2914."DEFVAL{500}::={ lmpNbrEntry 2}lmpNbrRetryLimit OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the maximum number of times a message
is transmitted without being acknowledged. A value of 0 is used
to indicate that a node should never stop retransmission.
This object along with lmpNbrRetransmitInterval is
used to implement congestion-handling mechanism as defined in
Section 10 of the Link Management Protocol specification,
which is based on RFC 2914."REFERENCE"Link Management Protocol, RFC 4204.
Congestion Control Principles, RFC 2914."DEFVAL{3}::={ lmpNbrEntry 3}lmpNbrRetransmitDelta OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object governs the speed with which the sender increases
the retransmission interval as explained in section 10 of the
Link Management Protocol specification, which is based on
RFC 2914. This value is a power used to express the
exponential backoff. The ratio of two successive retransmission
intervals is (1 + Delta)."REFERENCE"Link Management Protocol, RFC 4204.
Congestion Control Principles, RFC 2914."DEFVAL{1}::={ lmpNbrEntry 4}lmpNbrAdminStatus OBJECT-TYPESYNTAXINTEGER{ up(1), down(2)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The desired operational status of LMP to this remote node."::={ lmpNbrEntry 5}lmpNbrOperStatus OBJECT-TYPESYNTAXINTEGER{ up(1), down(2)}
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The actual operational status of LMP to this remote node."::={ lmpNbrEntry 6}lmpNbrRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."::={ lmpNbrEntry 7}lmpNbrStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row in the
lmpNbrTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."DEFVAL{ nonVolatile }::={ lmpNbrEntry 8}-- End of lmpNbrTablelmpCcHelloIntervalDefault OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies the default value for the HelloInterval
parameter used in the Hello protocol keep-alive phase. It
indicates how frequently LMP Hello messages will be sent. It
is used a the default value for lmpCcHelloInterval.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
REFERENCE"Link Management Protocol, RFC 4204"::={ lmpObjects 4}lmpCcHelloIntervalDefaultMin OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies the default minimum value for the
HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMin. Implementations should save the
value of this object in persistent memory so that it survives
restarts or reboot."::={ lmpObjects 5}lmpCcHelloIntervalDefaultMax OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies the default maximum value for the
HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMax. Implementations should save the
value of this object in persistent memory so that it survives
restarts or reboot."::={ lmpObjects 6}lmpCcHelloDeadIntervalDefault OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies the default HelloDeadInterval parameter
to use in the Hello protocol keep-alive phase. It indicates
how long a device should wait before declaring the control
channel dead. The HelloDeadInterval parameter should be at
least three times the value of HelloInterval. It is used as
a default value for lmpCcHelloDeadInterval. Implementations
should save the value of this object in persistent memory so
that it survives restarts or reboot."REFERENCE"Link Management Protocol, RFC 4204"
::={ lmpObjects 7}lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies the default minimum value for the
HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMin. Implementations should save
the value of this object in persistent memory so that it
survives restarts or reboot."::={ lmpObjects 8}lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies the default maximum value for the
HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMax. Implementations should save the
value of this object in persistent memory so that it survives
restarts or reboot."::={ lmpObjects 9}-- LMP Control Channel TablelmpControlChannelTable OBJECT-TYPESYNTAXSEQUENCEOF LmpControlChannelEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies LMP control channel information."::={ lmpObjects 10}lmpControlChannelEntry OBJECT-TYPESYNTAX LmpControlChannelEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table is created by a LMP-enabled device for
every control channel. Whenever a new entry is created with
lmpCcIsIf set to true(2), then a corresponding entry is
created in ifTable as well (see RFC 2863)."INDEX{ lmpCcId }::={ lmpControlChannelTable 1}
LmpControlChannelEntry ::=SEQUENCE{
lmpCcId Unsigned32,
lmpCcUnderlyingIfIndex InterfaceIndexOrZero,
lmpCcIsIf TruthValue,
lmpCcNbrNodeId LmpNodeId,
lmpCcRemoteId Unsigned32,
lmpCcRemoteAddressType InetAddressType,
lmpCcRemoteIpAddr InetAddress,
lmpCcSetupRole INTEGER,
lmpCcAuthentication TruthValue,
lmpCcHelloInterval LmpInterval,
lmpCcHelloIntervalMin LmpInterval,
lmpCcHelloIntervalMax LmpInterval,
lmpCcHelloIntervalNegotiated LmpInterval,
lmpCcHelloDeadInterval LmpInterval,
lmpCcHelloDeadIntervalMin LmpInterval,
lmpCcHelloDeadIntervalMax LmpInterval,
lmpCcHelloDeadIntervalNegotiated LmpInterval,
lmpCcLastChange TimeTicks,
lmpCcAdminStatus INTEGER,
lmpCcOperStatus INTEGER,
lmpCcRowStatus RowStatus,
lmpCcStorageType StorageType}lmpCcId OBJECT-TYPESYNTAXUnsigned32(1..4294967295)
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This value represents the local control channel identifier.
The control channel identifier is a non-zero 32-bit number."::={ lmpControlChannelEntry 1}lmpCcUnderlyingIfIndex OBJECT-TYPESYNTAXInterfaceIndexOrZeroMAX-ACCESSread-createSTATUScurrentDESCRIPTION"If lmpCcIsIf is set to true(1), this object carries the
index into the ifTable of the entry that represents the
LMP interface over which LMP will transmit its traffic.
If this object is set to zero, but lmpCcIsIf is set to
true(1), the control channel is not currently associated
with any underlying interface and the control channel's
operational status must not be up(1), nor should the
control channel forward or receive traffic.
If lmpCcIsIf is set to false(2), this object should be set
to zero and should be ignored."::={ lmpControlChannelEntry 2}lmpCcIsIf OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"In implementations where the control channels are modeled
as interfaces, the value of this object is true(1) and
this control channel is represented by an interface in
the interfaces group table as indicated by the value of
lmpCcUnderlyingIfIndex. If control channels are not
modeled as interfaces, the value of this object is
false(2) and there is no corresponding interface for
this control channel in the interfaces group table,
and the value of lmpCcUnderlyingIfIndex should be
ignored."::={ lmpControlChannelEntry 3}
lmpCcNbrNodeId OBJECT-TYPESYNTAXLmpNodeIdMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This is the Node ID of the control channel remote node.
This value either is configured or gets created by the node
when a Config message is received or when an outgoing Config
message is acknowledged by the remote node."::={ lmpControlChannelEntry 4}lmpCcRemoteId OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This value represents the remote control channel identifier
(32-bit number). It is determined during the negotiation
phase. A value of zero means that the remote control channel
identifier has not yet been learnt."::={ lmpControlChannelEntry 5}lmpCcRemoteAddressType OBJECT-TYPESYNTAXInetAddressTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This value represents the remote control channel IP address
type. In point-to-point configuration, this value can be set
to unknown(0)."::={ lmpControlChannelEntry 6}lmpCcRemoteIpAddr OBJECT-TYPESYNTAXInetAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This value represents the remote control channel Internet
address for numbered control channel. The type of this
address is determined by lmpCcRemoteAddressType.
Control channel must be numbered on non-point-to-point
configuration. For point-to-point configuration, the
remote control channel address can be of type unknown
in which case this object must be a zero-length string. The
lmpCcRemoteId object then identifies the unnumbered
address."::={ lmpControlChannelEntry 7}lmpCcSetupRole OBJECT-TYPESYNTAXINTEGER{ active(1), passive(2)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The role that this node should take during establishment
of this control channel. An active node will initiate
establishment. A passive node will wait for the remote node
to initiate. A pair of nodes that both take the passive role
will never establish communications."DEFVAL{ active }::={ lmpControlChannelEntry 8}lmpCcAuthentication OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object indicates whether the control channel must use
authentication."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpControlChannelEntry 9}lmpCcHelloInterval OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the value of the HelloInterval
parameter. The default value for this object should be
set to lmpCcHelloIntervalDefault."::={ lmpControlChannelEntry 10}
lmpCcHelloIntervalMin OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the minimum value for the
HelloInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMinDefault."::={ lmpControlChannelEntry 11}lmpCcHelloIntervalMax OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the maximum value for the
HelloInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMaxDefault."::={ lmpControlChannelEntry 12}lmpCcHelloIntervalNegotiated OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Once the control channel is active, this object represents
the negotiated HelloInterval value."::={ lmpControlChannelEntry 13}lmpCcHelloDeadInterval OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the value of the HelloDeadInterval
parameter. The default value for this object should be
set to lmpCcHelloDeadIntervalDefault."::={ lmpControlChannelEntry 14}lmpCcHelloDeadIntervalMin OBJECT-TYPE
SYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the minimum value for the
HelloDeadInterval parameter. The default value for this
object should be set to lmpCcHelloDeadIntervalMinDefault."::={ lmpControlChannelEntry 15}lmpCcHelloDeadIntervalMax OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the maximum value for the
HelloDeadInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMaxDefault."::={ lmpControlChannelEntry 16}lmpCcHelloDeadIntervalNegotiated OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Once the control channel is active, this object represents
the negotiated HelloDeadInterval value."::={ lmpControlChannelEntry 17}lmpCcLastChange OBJECT-TYPESYNTAXTimeTicksMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of sysUpTime at the time the control channel entered
its current operational state. If the current state was
entered prior to the last re-initialization of the local
network management subsystem, then this object contains a
zero value."::={ lmpControlChannelEntry 18}lmpCcAdminStatus OBJECT-TYPESYNTAXINTEGER{ up(1), down(2)}
MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The desired operational status of this control channel."::={ lmpControlChannelEntry 19}lmpCcOperStatus OBJECT-TYPESYNTAXINTEGER{up(1),down(2),configSnd(3),configRcv(4),active(5),goingDown(6)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The actual operational status of this control channel."::={ lmpControlChannelEntry 20}lmpCcRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."::={ lmpControlChannelEntry 21}
lmpCcStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row in the
lmpControlChannelTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."DEFVAL{ nonVolatile }::={ lmpControlChannelEntry 22}-- End of lmpControlChannelTable-- LMP Control Channel Performance TablelmpControlChannelPerfTable OBJECT-TYPESYNTAXSEQUENCEOF LmpControlChannelPerfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies LMP control channel performance
counters."::={ lmpObjects 11}lmpControlChannelPerfEntry OBJECT-TYPESYNTAX LmpControlChannelPerfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table is created by a LMP-enabled device for
every control channel. lmpCcCounterDiscontinuityTime is used
to indicate potential discontinuity for all counter objects
in this table."INDEX{ lmpCcId }::={ lmpControlChannelPerfTable 1}
LmpControlChannelPerfEntry ::=SEQUENCE{
lmpCcInOctets Counter32,
lmpCcInDiscards Counter32,
lmpCcInErrors Counter32,
lmpCcOutOctets Counter32,
lmpCcOutDiscards Counter32,
lmpCcOutErrors Counter32,
lmpCcConfigReceived Counter32,
lmpCcConfigSent Counter32,
lmpCcConfigRetransmit Counter32,
lmpCcConfigAckReceived Counter32,
lmpCcConfigAckSent Counter32,
lmpCcConfigNackReceived Counter32,
lmpCcConfigNackSent Counter32,
lmpCcHelloReceived Counter32,
lmpCcHelloSent Counter32,
lmpCcBeginVerifyReceived Counter32,
lmpCcBeginVerifySent Counter32,
lmpCcBeginVerifyRetransmit Counter32,
lmpCcBeginVerifyAckReceived Counter32,
lmpCcBeginVerifyAckSent Counter32,
lmpCcBeginVerifyNackReceived Counter32,
lmpCcBeginVerifyNackSent Counter32,
lmpCcEndVerifyReceived Counter32,
lmpCcEndVerifySent Counter32,
lmpCcEndVerifyRetransmit Counter32,
lmpCcEndVerifyAckReceived Counter32,
lmpCcEndVerifyAckSent Counter32,
lmpCcTestStatusSuccessReceived Counter32,
lmpCcTestStatusSuccessSent Counter32,
lmpCcTestStatusSuccessRetransmit Counter32,
lmpCcTestStatusFailureReceived Counter32,
lmpCcTestStatusFailureSent Counter32,
lmpCcTestStatusFailureRetransmit Counter32,
lmpCcTestStatusAckReceived Counter32,
lmpCcTestStatusAckSent Counter32,
lmpCcLinkSummaryReceived Counter32,
lmpCcLinkSummarySent Counter32,
lmpCcLinkSummaryRetransmit Counter32,
lmpCcLinkSummaryAckReceived Counter32,
lmpCcLinkSummaryAckSent Counter32,
lmpCcLinkSummaryNackReceived Counter32,
lmpCcLinkSummaryNackSent Counter32,
lmpCcChannelStatusReceived Counter32,
lmpCcChannelStatusSent Counter32,
lmpCcChannelStatusRetransmit Counter32,
lmpCcChannelStatusAckReceived Counter32,
lmpCcChannelStatusAckSent Counter32,
lmpCcChannelStatusReqReceived Counter32,
lmpCcChannelStatusReqSent Counter32,
lmpCcChannelStatusReqRetransmit Counter32,
lmpCcChannelStatusRspReceived Counter32,
lmpCcChannelStatusRspSent Counter32,
lmpCcCounterDiscontinuityTime TimeStamp}lmpCcInOctets OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of LMP message octets received on the
control channel."::={ lmpControlChannelPerfEntry 1}lmpCcInDiscards OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"The number of inbound packets that were chosen to be
discarded even though no errors had been detected. One
possible reason for discarding such a packet could be to
free up buffer space."::={ lmpControlChannelPerfEntry 2}lmpCcInErrors OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of inbound packets that contained errors
preventing them from being processed by LMP."::={ lmpControlChannelPerfEntry 3}lmpCcOutOctets OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of LMP message octets transmitted out of
the control channel."::={ lmpControlChannelPerfEntry 4}lmpCcOutDiscards OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of outbound packets that were chosen to be
discarded even though no errors had been detected to
prevent their being transmitted. One possible reason
for discarding such a packet could be to free up buffer
space."::={ lmpControlChannelPerfEntry 5}lmpCcOutErrors OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of outbound packets that could not be
transmitted because of errors."::={ lmpControlChannelPerfEntry 6}lmpCcConfigReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of Config messages that have
been received on this control channel."::={ lmpControlChannelPerfEntry 7}lmpCcConfigSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of Config messages that have
been sent on this control channel."::={ lmpControlChannelPerfEntry 8}lmpCcConfigRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of Config messages that
have been retransmitted over this control channel."::={ lmpControlChannelPerfEntry 9}lmpCcConfigAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ConfigAck messages that have
been received on this control channel."::={ lmpControlChannelPerfEntry 10}lmpCcConfigAckSent OBJECT-TYPESYNTAXCounter32
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ConfigAck messages that have
been sent on this control channel."::={ lmpControlChannelPerfEntry 11}lmpCcConfigNackReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ConfigNack messages that have
been received on this control channel."::={ lmpControlChannelPerfEntry 12}lmpCcConfigNackSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ConfigNack messages that have
been sent on this control channel."::={ lmpControlChannelPerfEntry 13}lmpCcHelloReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of Hello messages that have
been received on this control channel."::={ lmpControlChannelPerfEntry 14}lmpCcHelloSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of Hello messages that have
been sent on this control channel."::={ lmpControlChannelPerfEntry 15}
lmpCcBeginVerifyReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerify messages that have
been received on this control channel."::={ lmpControlChannelPerfEntry 16}lmpCcBeginVerifySent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerify messages that have
been sent on this control channel."::={ lmpControlChannelPerfEntry 17}lmpCcBeginVerifyRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerify messages that
have been retransmitted over this control channel."::={ lmpControlChannelPerfEntry 18}lmpCcBeginVerifyAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerifyAck messages that
have been received on this control channel."::={ lmpControlChannelPerfEntry 19}lmpCcBeginVerifyAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-only
STATUScurrentDESCRIPTION"This object counts the number of BeginVerifyAck messages that
have been sent on this control channel."::={ lmpControlChannelPerfEntry 20}lmpCcBeginVerifyNackReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerifyNack messages that
have been received on this control channel."::={ lmpControlChannelPerfEntry 21}lmpCcBeginVerifyNackSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerifyNack messages that
have been sent on this control channel."::={ lmpControlChannelPerfEntry 22}lmpCcEndVerifyReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerify messages that have
been received on this control channel."::={ lmpControlChannelPerfEntry 23}lmpCcEndVerifySent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerify messages that have
been sent on this control channel."::={ lmpControlChannelPerfEntry 24}
lmpCcEndVerifyRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerify messages that
have been retransmitted over this control channel."::={ lmpControlChannelPerfEntry 25}lmpCcEndVerifyAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerifyAck messages that
have been received on this control channel."::={ lmpControlChannelPerfEntry 26}lmpCcEndVerifyAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerifyAck messages that
have been sent on this control channel."::={ lmpControlChannelPerfEntry 27}lmpCcTestStatusSuccessReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusSuccess messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 28}lmpCcTestStatusSuccessSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-only
STATUScurrentDESCRIPTION"This object counts the number of TestStatusSuccess messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 29}lmpCcTestStatusSuccessRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusSuccess messages
that have been retransmitted over this control channel."::={ lmpControlChannelPerfEntry 30}lmpCcTestStatusFailureReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusFailure messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 31}lmpCcTestStatusFailureSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusFailure messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 32}lmpCcTestStatusFailureRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusFailure messages
that have been retransmitted over this control channel."
::={ lmpControlChannelPerfEntry 33}lmpCcTestStatusAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusAck messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 34}lmpCcTestStatusAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusAck messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 35}lmpCcLinkSummaryReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummary messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 36}lmpCcLinkSummarySent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummary messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 37}lmpCcLinkSummaryRetransmit OBJECT-TYPESYNTAXCounter32
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummary messages that
have been retransmitted over this control channel."::={ lmpControlChannelPerfEntry 38}lmpCcLinkSummaryAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryAck messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 39}lmpCcLinkSummaryAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryAck messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 40}lmpCcLinkSummaryNackReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryNack messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 41}lmpCcLinkSummaryNackSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryNack messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 42}lmpCcChannelStatusReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 43}lmpCcChannelStatusSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 44}lmpCcChannelStatusRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages
that have been retransmitted on this control channel."::={ lmpControlChannelPerfEntry 45}lmpCcChannelStatusAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusAck messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 46}lmpCcChannelStatusAckSent OBJECT-TYPE
SYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 47}lmpCcChannelStatusReqReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusRequest messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 48}lmpCcChannelStatusReqSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusRequest messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 49}lmpCcChannelStatusReqRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusRequest messages
that have been retransmitted on this control channel."::={ lmpControlChannelPerfEntry 50}lmpCcChannelStatusRspReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"This object counts the number of ChannelStatusResponse messages
that have been received on this control channel."::={ lmpControlChannelPerfEntry 51}lmpCcChannelStatusRspSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusResponse messages
that have been sent on this control channel."::={ lmpControlChannelPerfEntry 52}lmpCcCounterDiscontinuityTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of sysUpTime on the most recent occasion at which
any one or more of this control channel's counters suffered a
discontinuity. The relevant counters are the specific
instances associated with this control channel of any
Counter32 object contained in the lmpControlChannelPerfTable.
If no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this
object contains a zero value."::={ lmpControlChannelPerfEntry 53}-- End of lmpControlChannelPerfTable-- LMP TE Link TablelmpTeLinkTable OBJECT-TYPESYNTAXSEQUENCEOF LmpTeLinkEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies the LMP-specific TE link information.
Overall TE link information is kept in three separate tables:
ifTable for interface-specific information, lmpTeLinkTable
for LMP specific information, and teLinkTable for generic
TE link information. ifIndex is the common index to all
tables."::={ lmpObjects 12}lmpTeLinkEntry OBJECT-TYPESYNTAX LmpTeLinkEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table exists for each ifEntry with an
ifType of teLink(200) that is managed by LMP. An ifEntry with
an ifIndex must exist before the corresponding lmpTeLinkEntry is
created. If a TE link entry in the ifTable is destroyed, then
so is the corresponding entry in the lmpTeLinkTable. The
administrative status value is controlled from the ifEntry.
Setting the administrative status to testing prompts LMP to
start link verification on the TE link. Information about the
TE link that is not LMP specific is contained in teLinkTable of
the TE-LINK-STD-MIB MIB module."INDEX{ ifIndex }::={ lmpTeLinkTable 1}
LmpTeLinkEntry ::=SEQUENCE{
lmpTeLinkNbrRemoteNodeId LmpNodeId,
lmpTeLinkVerification TruthValue,
lmpTeLinkFaultManagement TruthValue,
lmpTeLinkDwdm TruthValue,
lmpTeLinkOperStatus INTEGER,
lmpTeLinkRowStatus RowStatus,
lmpTeLinkStorageType StorageType}lmpTeLinkNbrRemoteNodeId OBJECT-TYPESYNTAXLmpNodeIdMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This is the Node ID of the TE link remote node. This value
may be learned during control channel parameter negotiation
phase (in the Config message). Node ID is an address whose
type must be IPv4."::={ lmpTeLinkEntry 1}
lmpTeLinkVerification OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object indicates if the LMP link verification procedure
is enabled for this TE link."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpTeLinkEntry 2}lmpTeLinkFaultManagement OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object indicates if the LMP fault management procedure
is enabled on this TE link."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpTeLinkEntry 3}lmpTeLinkDwdm OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object indicates if the LMP DWDM procedure is enabled
on this TE link."REFERENCE"Link Management Protocol (LMP) for Dense Wavelength Division
Multiplexing (DWDM) Optical Line Systems, RFC 4209"::={ lmpTeLinkEntry 4}lmpTeLinkOperStatus OBJECT-TYPESYNTAXINTEGER{up(1), down(2), testing(3), init(4), degraded(5)
}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The actual operational status of this TE link. The status
is set to testing when the TE link is performing link
verification. A degraded state indicates that there is
no active control channel between the pair of nodes that
form the endpoints of the TE link, but yet at least one
data-bearing link on the TE link is allocated."::={ lmpTeLinkEntry 5}lmpTeLinkRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."::={ lmpTeLinkEntry 6}lmpTeLinkStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row in the
lmpTeLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."DEFVAL{ nonVolatile }::={ lmpTeLinkEntry 7}-- End of lmpTeLinkTablelmpGlobalLinkVerificationInterval OBJECT-TYPESYNTAXUnsigned32UNITS"milliseconds"MAX-ACCESSread-writeSTATUScurrent
DESCRIPTION"This object indicates how often the link verification
procedure is executed. The interval is in milliseconds.
A value of 0 is used to indicate that the link
verification procedure should not be executed. The
interval specified in this object should be large enough
to allow the verification procedure to be completed
before the start of the next interval.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."::={ lmpObjects 13}-- LMP Link Verification TablelmpLinkVerificationTable OBJECT-TYPESYNTAXSEQUENCEOF LmpLinkVerificationEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies TE link information associated with the
LMP verification procedure."::={ lmpObjects 14}lmpLinkVerificationEntry OBJECT-TYPESYNTAX LmpLinkVerificationEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table is created by an LMP-enabled device for
every TE link that supports the LMP verification
procedure."INDEX{ ifIndex }::={ lmpLinkVerificationTable 1}
LmpLinkVerificationEntry ::=SEQUENCE{
lmpLinkVerifyInterval LmpInterval,
lmpLinkVerifyDeadInterval LmpInterval,
lmpLinkVerifyTransportMechanism BITS,
lmpLinkVerifyAllLinks TruthValue,
lmpLinkVerifyTransmissionRate Unsigned32,
lmpLinkVerifyWavelength Unsigned32,
lmpLinkVerifyRowStatus RowStatus,
lmpLinkVerifyStorageType StorageType}lmpLinkVerifyInterval OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the VerifyInterval parameter used
in the LMP link verification process. It indicates the
interval at which the Test messages are sent."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpLinkVerificationEntry 1}lmpLinkVerifyDeadInterval OBJECT-TYPESYNTAXLmpIntervalMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies the VerifyDeadInterval parameter used
in the verification of the physical connectivity of data-
bearing links. It specifies the observation period used to
detect a Test message at the remote node."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpLinkVerificationEntry 2}lmpLinkVerifyTransportMechanism OBJECT-TYPESYNTAXBITS{-- All encoding types:payload(0),-- SONET/SDH encoding type:dccSectionOverheadBytes(1),dccLineOverheadBytes(2),j0Trace(3),j1Trace(4),
j2Trace(5)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This defines the transport mechanism for the Test messages. The
scope of this bit mask is restricted to each link encoding
type. The local node will set the bits corresponding to the
various mechanisms it can support for transmitting LMP Test
messages. The receiver chooses the appropriate mechanism in the
BeginVerifyAck message."REFERENCE"Link Management Protocol, RFC 4204
Synchronous Optical Network (SONET)/Synchronous Digital
Hierarchy (SDH) Encoding for Link Management Protocol (LMP)
Test Messages, RFC 4207"::={ lmpLinkVerificationEntry 3}lmpLinkVerifyAllLinks OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"A value of true(2) for this object indicates that the
verification process checks all unallocated links, otherwise
only the new ports or component links that have been added to
this TE link are verified."::={ lmpLinkVerificationEntry 4}lmpLinkVerifyTransmissionRate OBJECT-TYPESYNTAXUnsigned32UNITS"bytes per second"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This is the transmission rate of the data link over which
the Test messages will be transmitted and is expressed in
bytes per second."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpLinkVerificationEntry 5}
lmpLinkVerifyWavelength OBJECT-TYPESYNTAXUnsigned32UNITS"nanometers"MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This value corresponds to the wavelength at
which the Test messages will be transmitted and is
measured in nanometers (nm). If each data-bearing link
corresponds to a separate wavelength, then this value should
be set to 0."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpLinkVerificationEntry 6}lmpLinkVerifyRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."::={ lmpLinkVerificationEntry 7}lmpLinkVerifyStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row in the
lmpLinkVerificationTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."DEFVAL{ nonVolatile }::={ lmpLinkVerificationEntry 8}-- End of lmpLinkVerificationTable-- LMP TE Link Performance TablelmpTeLinkPerfTable OBJECT-TYPE
SYNTAXSEQUENCEOF LmpTeLinkPerfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies LMP TE link performance counters."::={ lmpObjects 15}lmpTeLinkPerfEntry OBJECT-TYPESYNTAX LmpTeLinkPerfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table is created by an LMP-enabled device for
every TE link. lmpTeCounterDiscontinuityTime is used
to indicate potential discontinuity for all counter objects
in this table."INDEX{ ifIndex }::={ lmpTeLinkPerfTable 1}
LmpTeLinkPerfEntry ::=SEQUENCE{
lmpTeInOctets Counter32,
lmpTeOutOctets Counter32,
lmpTeBeginVerifyReceived Counter32,
lmpTeBeginVerifySent Counter32,
lmpTeBeginVerifyRetransmit Counter32,
lmpTeBeginVerifyAckReceived Counter32,
lmpTeBeginVerifyAckSent Counter32,
lmpTeBeginVerifyNackReceived Counter32,
lmpTeBeginVerifyNackSent Counter32,
lmpTeEndVerifyReceived Counter32,
lmpTeEndVerifySent Counter32,
lmpTeEndVerifyRetransmit Counter32,
lmpTeEndVerifyAckReceived Counter32,
lmpTeEndVerifyAckSent Counter32,
lmpTeTestStatusSuccessReceived Counter32,
lmpTeTestStatusSuccessSent Counter32,
lmpTeTestStatusSuccessRetransmit Counter32,
lmpTeTestStatusFailureReceived Counter32,
lmpTeTestStatusFailureSent Counter32,
lmpTeTestStatusFailureRetransmit Counter32,
lmpTeTestStatusAckReceived Counter32,
lmpTeTestStatusAckSent Counter32,
lmpTeLinkSummaryReceived Counter32,
lmpTeLinkSummarySent Counter32,
lmpTeLinkSummaryRetransmit Counter32,
lmpTeLinkSummaryAckReceived Counter32,
lmpTeLinkSummaryAckSent Counter32,
lmpTeLinkSummaryNackReceived Counter32,
lmpTeLinkSummaryNackSent Counter32,
lmpTeChannelStatusReceived Counter32,
lmpTeChannelStatusSent Counter32,
lmpTeChannelStatusRetransmit Counter32,
lmpTeChannelStatusAckReceived Counter32,
lmpTeChannelStatusAckSent Counter32,
lmpTeChannelStatusReqReceived Counter32,
lmpTeChannelStatusReqSent Counter32,
lmpTeChannelStatusReqRetransmit Counter32,
lmpTeChannelStatusRspReceived Counter32,
lmpTeChannelStatusRspSent Counter32,
lmpTeCounterDiscontinuityTime TimeStamp}lmpTeInOctets OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of LMP message octets received for
this TE link."::={ lmpTeLinkPerfEntry 1}lmpTeOutOctets OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of LMP message octets transmitted out
for this TE link."::={ lmpTeLinkPerfEntry 2}lmpTeBeginVerifyReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerify messages that have
been received for this TE link."::={ lmpTeLinkPerfEntry 3}lmpTeBeginVerifySent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerify messages that have
been sent for this TE link."::={ lmpTeLinkPerfEntry 4}lmpTeBeginVerifyRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerify messages that
have been retransmitted for this TE link."::={ lmpTeLinkPerfEntry 5}lmpTeBeginVerifyAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-only
STATUScurrentDESCRIPTION"This object counts the number of BeginVerifyAck messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 6}lmpTeBeginVerifyAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerifyAck messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 7}lmpTeBeginVerifyNackReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerifyNack messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 8}lmpTeBeginVerifyNackSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of BeginVerifyNack messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 9}lmpTeEndVerifyReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerify messages that have
been received for this TE link."::={ lmpTeLinkPerfEntry 10}
lmpTeEndVerifySent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerify messages that have
been sent for this TE link."::={ lmpTeLinkPerfEntry 11}lmpTeEndVerifyRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerify messages that
have been retransmitted over this control channel."::={ lmpTeLinkPerfEntry 12}lmpTeEndVerifyAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerifyAck messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 13}lmpTeEndVerifyAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of EndVerifyAck messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 14}lmpTeTestStatusSuccessReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"This object counts the number of TestStatusSuccess messages
that have been received for this TE link."::={ lmpTeLinkPerfEntry 15}lmpTeTestStatusSuccessSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusSuccess messages
that have been sent for this TE link."::={ lmpTeLinkPerfEntry 16}lmpTeTestStatusSuccessRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusSuccess messages
that have been retransmitted for this TE link."::={ lmpTeLinkPerfEntry 17}lmpTeTestStatusFailureReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusFailure messages
that have been received for this TE link."::={ lmpTeLinkPerfEntry 18}lmpTeTestStatusFailureSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusFailure messages
that have been sent for this TE link."::={ lmpTeLinkPerfEntry 19}
lmpTeTestStatusFailureRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusFailure messages
that have been retransmitted on this TE link."::={ lmpTeLinkPerfEntry 20}lmpTeTestStatusAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusAck messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 21}lmpTeTestStatusAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of TestStatusAck messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 22}lmpTeLinkSummaryReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummary messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 23}lmpTeLinkSummarySent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"This object counts the number of LinkSummary messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 24}lmpTeLinkSummaryRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummary messages that
have been retransmitted over this control channel."::={ lmpTeLinkPerfEntry 25}lmpTeLinkSummaryAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryAck messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 26}lmpTeLinkSummaryAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryAck messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 27}lmpTeLinkSummaryNackReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryNack messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 28}lmpTeLinkSummaryNackSent OBJECT-TYPE
SYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of LinkSummaryNack messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 29}lmpTeChannelStatusReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages that
have been received for this TE link."::={ lmpTeLinkPerfEntry 30}lmpTeChannelStatusSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages that
have been sent for this TE link."::={ lmpTeLinkPerfEntry 31}lmpTeChannelStatusRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages that
have been retransmitted for this TE link."::={ lmpTeLinkPerfEntry 32}lmpTeChannelStatusAckReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusAck messages
that have been received for this TE link."::={ lmpTeLinkPerfEntry 33}lmpTeChannelStatusAckSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatus messages
that have been sent for this TE link."::={ lmpTeLinkPerfEntry 34}lmpTeChannelStatusReqReceived OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusRequest messages
that have been received for this TE link."::={ lmpTeLinkPerfEntry 35}lmpTeChannelStatusReqSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusRequest messages
that have been sent for this TE link."::={ lmpTeLinkPerfEntry 36}lmpTeChannelStatusReqRetransmit OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusRequest messages
that have been retransmitted for this TE link."::={ lmpTeLinkPerfEntry 37}lmpTeChannelStatusRspReceived OBJECT-TYPESYNTAXCounter32
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusResponse messages
that have been received for this TE link."::={ lmpTeLinkPerfEntry 38}lmpTeChannelStatusRspSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of ChannelStatusResponse messages
that have been sent for this TE link."::={ lmpTeLinkPerfEntry 39}lmpTeCounterDiscontinuityTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of sysUpTime on the most recent occasion at which
any one or more of this TE link's counters suffered a
discontinuity. The relevant counters are the specific
instances associated with this TE link of any Counter32
object contained in the lmpTeLinkPerfTable. If
no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this
object contains a zero value."::={ lmpTeLinkPerfEntry 40}-- End of lmpTeLinkPerfTable-- LMP Data Link TablelmpDataLinkTable OBJECT-TYPESYNTAXSEQUENCEOF LmpDataLinkEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies the data-bearing links managed by the
LMP."::={ lmpObjects 16}
lmpDataLinkEntry OBJECT-TYPESYNTAX LmpDataLinkEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table exists for each ifEntry that represents
a data-bearing link. An ifEntry with an ifIndex must exist
before the corresponding lmpDataLinkEntry is created.
If an entry representing the data-bearing link is destroyed in
the ifTable, then so is the corresponding entry in the
lmpDataLinkTable. The administrative status value is
controlled from the ifEntry. The index to this table is also
used to get information in the componentLinkTable
of the TE-LINK-STD-MIB MIB module."INDEX{ ifIndex }::={ lmpDataLinkTable 1}
LmpDataLinkEntry ::=SEQUENCE{
lmpDataLinkType INTEGER,
lmpDataLinkAddressType InetAddressType,
lmpDataLinkIpAddr InetAddress,
lmpDataLinkRemoteIpAddress InetAddress,
lmpDataLinkRemoteIfId InterfaceIndexOrZero,
lmpDataLinkEncodingType TeLinkEncodingType,
lmpDataLinkActiveOperStatus INTEGER,
lmpDataLinkPassiveOperStatus INTEGER,
lmpDataLinkRowStatus RowStatus,
lmpDataLinkStorageType StorageType}lmpDataLinkType OBJECT-TYPESYNTAXINTEGER{port(1),componentLink(2)}MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"This attribute specifies whether this data-bearing link is
a port or a component link. Component link are multiplex
capable, whereas ports are not multiplex capable."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpDataLinkEntry 1}lmpDataLinkAddressType OBJECT-TYPESYNTAXInetAddressTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This attribute specifies the data-bearing link IP address
type. If the data-bearing link is unnumbered, the address
type must be set to unknown(0)."::={ lmpDataLinkEntry 2}lmpDataLinkIpAddr OBJECT-TYPESYNTAXInetAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The local Internet address for numbered links. The type
of this address is determined by the value of
lmpDataLinkAddressType object.
For IPv4 and IPv6 numbered links, this object represents
the local IP address associated with the data-bearing
link. For an unnumbered link, the local address is
of type unknown and this object is set to the zero-length
string and the ifIndex object then identifies the
unnumbered address."::={ lmpDataLinkEntry 3}lmpDataLinkRemoteIpAddress OBJECT-TYPESYNTAXInetAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The remote Internet address for numbered data-bearing links.
The type of this address is determined by the
lmpDataLinkAddressType object.
For IPv4 and IPv6 numbered links, this object represents the
remote IP address associated with the data-bearing link. For
an unnumbered link, the remote address is of type unknown
and this object is set to the zero-length string and the
lmpDataLinkRemoteIfId object then identifies the unnumbered
address.
This information is either configured manually or
communicated by the remote node during the link verification
procedure."::={ lmpDataLinkEntry 4}lmpDataLinkRemoteIfId OBJECT-TYPESYNTAXInterfaceIndexOrZeroMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Interface identifier of the remote end point. This
information is either configured manually or
communicated by the remote node during the link verification
procedure."::={ lmpDataLinkEntry 5}lmpDataLinkEncodingType OBJECT-TYPESYNTAXTeLinkEncodingTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The encoding type of the data-bearing link."REFERENCE"Generalized MPLS Signaling Functional Description, RFC 3471"::={ lmpDataLinkEntry 6}lmpDataLinkActiveOperStatus OBJECT-TYPESYNTAXINTEGER{upAlloc(1),upFree(2),down(3),testing(4)}MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"The actual operational status of this data-bearing link
(active FSM)."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpDataLinkEntry 7}lmpDataLinkPassiveOperStatus OBJECT-TYPESYNTAXINTEGER{upAlloc(1),upFree(2),down(3),psvTst(4)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The actual operational status of this data-bearing link
(passive FSM)."REFERENCE"Link Management Protocol, RFC 4204"::={ lmpDataLinkEntry 8}lmpDataLinkRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."::={ lmpDataLinkEntry 9}lmpDataLinkStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row in the
lmpDataLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."DEFVAL{ nonVolatile }::={ lmpDataLinkEntry 10}-- End of lmpDataLinkTable-- LMP Data Link Performance TablelmpDataLinkPerfTable OBJECT-TYPESYNTAXSEQUENCEOF LmpDataLinkPerfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table specifies the data-bearing links LMP performance
counters."::={ lmpObjects 17}lmpDataLinkPerfEntry OBJECT-TYPESYNTAX LmpDataLinkPerfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table contains information about
the LMP performance counters for the data-bearing links.
lmpDataLinkDiscontinuityTime is used to indicate potential
discontinuity for all counter objects in this table."INDEX{ ifIndex }::={ lmpDataLinkPerfTable 1}
LmpDataLinkPerfEntry ::=SEQUENCE{
lmpDataLinkTestReceived Counter32,
lmpDataLinkTestSent Counter32,
lmpDataLinkActiveTestSuccess Counter32,
lmpDataLinkActiveTestFailure Counter32,
lmpDataLinkPassiveTestSuccess Counter32,
lmpDataLinkPassiveTestFailure Counter32,
lmpDataLinkDiscontinuityTime TimeStamp}lmpDataLinkTestReceived OBJECT-TYPE
SYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of Test messages that have
been received on this data-bearing link."::={ lmpDataLinkPerfEntry 1}lmpDataLinkTestSent OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of Test messages that have
been sent on this data-bearing link."::={ lmpDataLinkPerfEntry 2}lmpDataLinkActiveTestSuccess OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of data-bearing link tests
that were successful on the active side of this data-
bearing link."::={ lmpDataLinkPerfEntry 3}lmpDataLinkActiveTestFailure OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of data-bearing link tests
that failed on the active side of this data-bearing link."::={ lmpDataLinkPerfEntry 4}lmpDataLinkPassiveTestSuccess OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"This object counts the number of data-bearing link tests
that were successful on the passive side of this data-
bearing link."::={ lmpDataLinkPerfEntry 5}lmpDataLinkPassiveTestFailure OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object counts the number of data-bearing link tests
that failed on the passive side of this data-bearing link."::={ lmpDataLinkPerfEntry 6}lmpDataLinkDiscontinuityTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of sysUpTime on the most recent occasion at which
any one or more of this data-bearing link's counters suffered
a discontinuity. The relevant counters are the specific
instances associated with this data-bearing link of any
Counter32 object contained in the lmpDataLinkPerfTable. If
no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this
object contains a zero value."::={ lmpDataLinkPerfEntry 7}-- End of lmpDataLinkPerfTable-- Notification ConfigurationlmpNotificationMaxRate OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The LMP notification rate depends on the size of the network,
the type of links, the network configuration, the
reliability of the network, etc.
When designing this MIB, care has been taken to minimize the
amount of notifications generated for LMP purposes. Wherever
possible, notifications are state driven, meaning the
notifications are sent only when the system changes state.
The only notifications that are repeated and could cause a
problem as far as congestion is concerned are the ones
associated with data link verification.
Without any considerations to handling of these
notifications, a problem may arise if the number of data
links is high. Since the data link verification notifications
can happen only once per data link per link verification
interval, the notification rate should be sustainable if one
chooses an appropriate link verification interval for a given
network configuration. For instance, a network of 100 nodes
with 5 links of 128 wavelengths each and a link verification
of 1 minute with no more than 10% of the links failed at any
given time would have 1 notification per second sent from
each node, or 100 notifications per second for the whole
network. The rest of the notifications are negligible
compared to this number.
To alleviate the congestion problem, the
lmpNotificationMaxRate object can be used to implement a
throttling mechanism. It is also possible to enable/disable
certain type of notifications.
This variable indicates the maximum number of
notifications issued per minute. If events occur
more rapidly, the implementation may simply fail to
emit these notifications during that period, or may
queue them until an appropriate time. A value of 0
means no throttling is applied and events may be
notified at the rate at which they occur.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."::={ lmpObjects 18}lmpLinkPropertyNotificationsEnabled OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"If this object is true, then it enables the
generation of lmpTeLinkPropertyMismatch
and lmpDataLinkPropertyMismatch notifications,
otherwise these notifications are not emitted.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."DEFVAL{ false }
::={ lmpObjects 19}lmpUnprotectedNotificationsEnabled OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"If this object is true, then it enables the
generation of lmpUnprotected notifications,
otherwise these notifications are not emitted.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."DEFVAL{ false }::={ lmpObjects 20}lmpCcUpDownNotificationsEnabled OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"If this object is true, then it enables the generation of
lmpControlChannelUp and lmpControlChannelDown notifications,
otherwise these notifications are not emitted.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."DEFVAL{ false }::={ lmpObjects 21}lmpTeLinkNotificationsEnabled OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"If this object is true, then it enables the
generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded
notifications, otherwise these notifications are not emitted.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."DEFVAL{ false }::={ lmpObjects 22}
lmpDataLinkNotificationsEnabled OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"If this object is true, then it enables the
generation of lmpDataLinkVerificationFailure
notification, otherwise these notifications are not emitted.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."DEFVAL{ false }::={ lmpObjects 23}-- Notifications-- Link Property Mismatch NotificationslmpTeLinkPropertyMismatch NOTIFICATION-TYPEOBJECTS{ teLinkRemoteIpAddr,
teLinkIncomingIfId }STATUScurrentDESCRIPTION"This notification is generated when a TE link property
mismatch is detected on the node. The received remote TE link
ID of the misconfigured TE link is represented by either
teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether
the TE link is numbered or unnumbered. This notification
should not be sent unless lmpLinkPropertyNotificationsEnabled
is true. It is recommended that this notification be reported
only the first time a mismatch is detected. Otherwise, for a
given TE link, this notification can occur no more than once
per verification interval (lmpGlobalLinkVerificationInterval)."::={ lmpNotifications 1}lmpDataLinkPropertyMismatch NOTIFICATION-TYPEOBJECTS{ lmpDataLinkType, lmpDataLinkRemoteIfId }STATUScurrentDESCRIPTION"This notification is generated when a data-bearing link
property mismatch is detected on the node. lmpDataLinkType
is used to identify the local identifiers associated with
the data link (the data link interface index can be used
to determine the TE link interface index as this
relationship is captured in the interface stack table).
The remote entity interface ID is the remote entity
interface ID received in the LinkSummary message.
This notification should not be sent unless
lmpLinkPropertyNotificationsEnabled is true. It is
recommended that this notification be reported only the
first time a mismatch is detected. Otherwise, for a given
data link, this notification can occur no more than once
per verification interval (lmpGlobalLinkVerificationInterval)."::={ lmpNotifications 2}-- Neighbor NotificationlmpUnprotected NOTIFICATION-TYPEOBJECTS{ lmpCcNbrNodeId }STATUScurrentDESCRIPTION"This notification is generated when there are more than one
control channels between LMP neighbors and the last redundant
control channel has failed. If the remaining operational
control channel fails, then there will be no more control
channels between the pair of nodes and all the TE links
between the pair of nodes will go to degraded state. This
notification should not be sent unless
lmpUnprotectedNotificationsEnabled is set to true."::={ lmpNotifications 3}-- Control Channel NotificationslmpControlChannelUp NOTIFICATION-TYPEOBJECTS{ lmpCcAdminStatus, lmpCcOperStatus }STATUScurrentDESCRIPTION"This notification is generated when a control
channel transitions to the up operational state. This
notification should not be sent unless
lmpCcUpDownNotificationsEnabled is true."::={ lmpNotifications 4}lmpControlChannelDown NOTIFICATION-TYPE
OBJECTS{ lmpCcAdminStatus, lmpCcOperStatus }STATUScurrentDESCRIPTION"This notification is generated when a control channel
transitions out of the up operational state. This
notification should not be sent unless
lmpCcUpDownNotificationsEnabled is true."::={ lmpNotifications 5}-- TE Link NotificationlmpTeLinkDegraded NOTIFICATION-TYPEOBJECTS{ lmpTeLinkOperStatus }STATUScurrentDESCRIPTION"This notification is generated when a lmpTeLinkOperStatus
object for a TE link enters the degraded state. This
notification should not be sent unless
lmpTeLinkNotificationsEnabled is true."::={ lmpNotifications 6}lmpTeLinkNotDegraded NOTIFICATION-TYPEOBJECTS{ lmpTeLinkOperStatus }STATUScurrentDESCRIPTION"This notification is generated when a lmpTeLinkOperStatus
object for a TE link leaves the degraded state. This
notification should not be sent unless
lmpTeLinkNotificationsEnabled is true."::={ lmpNotifications 7}-- Data-bearing Link NotificationlmpDataLinkVerificationFailure NOTIFICATION-TYPEOBJECTS{ lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus }STATUScurrentDESCRIPTION"This notification is generated when a data-bearing
link verification fails. This notification should not be sent
unless lmpDataLinkNotificationsEnabled is true. For a given
data link, this notification can occur no more than once per
verification interval (lmpGlobalLinkVerificationInterval)."::={ lmpNotifications 8}-- End of notifications-- Module compliancelmpCompliances
OBJECTIDENTIFIER::={ lmpConformance 1}lmpGroups
OBJECTIDENTIFIER::={ lmpConformance 2}lmpModuleFullCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"Compliance statement for agents that support the
configuration and monitoring of LMP MIB."MODULE-- this moduleMANDATORY-GROUPS{ lmpNodeGroup,
lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup,
lmpPerfGroup,
lmpTeLinkGroup,
lmpDataLinkGroup }GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION"This group is mandatory for devices that support
control channels that are not interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning false(1)."GROUP lmpCcIsInterfaceGroup
DESCRIPTION"This group is mandatory for devices that support
control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)."GROUP lmpLinkVerificationGroup
DESCRIPTION"This group is mandatory for devices that support
the link verification procedure."GROUP lmpNotificationGroup
DESCRIPTION"This group is optional."
-- lmpNbrTableOBJECT lmpNbrRowStatus
SYNTAXRowStatus{ active(1), notInService(2)}WRITE-SYNTAXRowStatus{ active(1), notInService(2),
createAndGo(4), destroy(6)}DESCRIPTION"Support for notReady(3) and createAndWait(5) is
not required."-- lmpControlChannelTableOBJECT lmpCcRemoteAddressType
SYNTAXINTEGER{ unknown(0), ipv4(1), ipv6(2)}DESCRIPTION"Only ipv4(1) and ipv6(2) address types need to be
supported for non-point-to-point configurations."OBJECT lmpCcRemoteIpAddr
SYNTAXInetAddress(SIZE(0|4|16))DESCRIPTION"The size of the IP address depends on the address type."OBJECT lmpCcRowStatus
SYNTAXRowStatus{ active(1), notInService(2)}WRITE-SYNTAXRowStatus{ active(1), notInService(2),
createAndGo(4), destroy(6)}DESCRIPTION"Support for notReady(3) and createAndWait(5) is
not required."OBJECT lmpCcOperStatus
SYNTAXINTEGER{ up(1), down(2)}DESCRIPTION"A value of configSnd(3), configRcv(4), active(5),
goingDown(6) need not be supported."-- lmpTeLinkTableOBJECT lmpTeLinkOperStatus
SYNTAXINTEGER{ up(1), down(2), degraded(5)}DESCRIPTION"The testing(3) and init(4) state need not be supported."OBJECT lmpTeLinkRowStatus
SYNTAXRowStatus{ active(1), notInService(2)}WRITE-SYNTAXRowStatus{ active(1), notInService(2),
createAndGo(4), destroy(6)}DESCRIPTION"Support for notReady(3) and createAndWait(5) is
not required."-- lmpDataLinkTableOBJECT lmpDataLinkActiveOperStatus
SYNTAXINTEGER{ upAlloc(1), upFree(2), down(3)}
DESCRIPTION"A value of testing(4) need not be supported."OBJECT lmpDataLinkPassiveOperStatus
SYNTAXINTEGER{ upAlloc(1), upFree(2), down(3)}DESCRIPTION"A value of psvTst(4) need not be supported."OBJECT lmpDataLinkRowStatus
SYNTAXRowStatus{ active(1), notInService(2)}WRITE-SYNTAXRowStatus{ active(1), notInService(2),
createAndGo(4), destroy(6)}DESCRIPTION"Support for notReady(3) and createAndWait(5) is
not required."::={ lmpCompliances 1}lmpModuleReadOnlyCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"Compliance statement for agents that support the
monitoring of the LMP MIB."MODULE-- this module-- The mandatory groups have to be implemented-- by all LMP-enabled devices. However, they may all be supported-- as read-only objects in the case where manual-- configuration is not supported.
MANDATORY-GROUPS{ lmpNodeGroup,
lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup,
lmpPerfGroup,
lmpTeLinkGroup,
lmpDataLinkGroup }GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION"This group is mandatory for devices that support
control channels that are not interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning false(1)."GROUP lmpCcIsInterfaceGroup
DESCRIPTION"This group is mandatory for devices that support
control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)."GROUP lmpLinkVerificationGroup
DESCRIPTION"This group is mandatory for devices that support
the link verification procedure."GROUP lmpNotificationGroup
DESCRIPTION"This group is optional."-- ScalarsOBJECT lmpAdminStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpGlobalLinkVerificationInterval
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloIntervalDefault
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloIntervalDefaultMin
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloIntervalDefaultMax
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloDeadIntervalDefault
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloDeadIntervalDefaultMin
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloDeadIntervalDefaultMax
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpNotificationMaxRate
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."-- lmpNbrTableOBJECT lmpNbrRetransmitInterval
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpNbrRetryLimit
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpNbrRetransmitDelta
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpNbrRowStatus
SYNTAXRowStatus{ active(1)}MIN-ACCESSread-onlyDESCRIPTION"Write access is not required, and active(1) is the
only status that needs to be supported."OBJECT lmpNbrStorageType
MIN-ACCESSread-onlyDESCRIPTION
"Write access is not required."-- lmpControlChannelTableOBJECT lmpCcUnderlyingIfIndex
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcIsIf
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcNbrNodeId
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcRemoteAddressType
SYNTAXINTEGER{ unknown(0), ipv4(1), ipv6(2)}MIN-ACCESSread-onlyDESCRIPTION"Only ipv4(1) and ipv6(2) address types need to be
supported for non-point-to-point configurations."OBJECT lmpCcRemoteIpAddr
SYNTAXInetAddress(SIZE(0|4|16))MIN-ACCESSread-onlyDESCRIPTION"The size of the IP address depends on the address type."OBJECT lmpCcSetupRole
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcAuthentication
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloIntervalMin
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."
OBJECT lmpCcHelloIntervalMax
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloDeadIntervalMin
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcHelloDeadIntervalMax
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpCcRowStatus
SYNTAXRowStatus{ active(1)}MIN-ACCESSread-onlyDESCRIPTION"Write access is not required, and active(1) is the
only status that needs to be supported."OBJECT lmpCcOperStatus
SYNTAXINTEGER{ up(1), down(2)}DESCRIPTION"A value of configSnd(3), configRcv(4), active(5),
goingDown(6) need not be supported."OBJECT lmpCcStorageType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."-- lmpLinkVerificationTableOBJECT lmpLinkVerifyInterval
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpLinkVerifyDeadInterval
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpLinkVerifyAllLinks
MIN-ACCESSread-only
DESCRIPTION"Write access is not required."-- lmpTeLinkTableOBJECT lmpTeLinkNbrRemoteNodeId
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required if the link verification
procedure is enabled."OBJECT lmpTeLinkVerification
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpTeLinkFaultManagement
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpTeLinkDwdm
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpTeLinkOperStatus
SYNTAXINTEGER{ up(1), down(2), degraded(5)}DESCRIPTION"The testing(3) and init(4) state need not be supported."OBJECT lmpTeLinkRowStatus
SYNTAXRowStatus{ active(1)}MIN-ACCESSread-onlyDESCRIPTION"Write access is not required, and active(1) is the
only status that needs to be supported."OBJECT lmpTeLinkStorageType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."-- lmpTeLinkVerificationTableOBJECT lmpLinkVerifyTransmissionRate
MIN-ACCESSread-only
DESCRIPTION"Write access is not required."OBJECT lmpLinkVerifyWavelength
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpLinkVerifyRowStatus
SYNTAXRowStatus{ active(1)}MIN-ACCESSread-onlyDESCRIPTION"Write access is not required, and active(1) is the
only status that needs to be supported."OBJECT lmpLinkVerifyStorageType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."-- lmpDataLinkTableOBJECT lmpDataLinkAddressType
SYNTAXINTEGER{ unknown(0), ipv4(1), ipv6(2)}MIN-ACCESSread-onlyDESCRIPTION"Only ipv4(1) and ipv6(2) address types need to be
supported for numbered links. For unnumbered links, the
unknown(0) address type needs to be supported."OBJECT lmpDataLinkIpAddr
SYNTAXInetAddress(SIZE(0|4|16))MIN-ACCESSread-onlyDESCRIPTION"Size of data-bearing link IP address depends on type
of data-bearing link. Data-bearing link IP address size
is zero if link is unnumbered, four if link IP address is
IPv4, and sixteen if link IP address is IPv6."OBJECT lmpDataLinkRemoteIpAddress
SYNTAXInetAddress(SIZE(0|4|16))MIN-ACCESSread-onlyDESCRIPTION"Write access is not required if the link verification
procedure is enabled."OBJECT lmpDataLinkRemoteIfId
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required if the link verification
procedure is enabled."OBJECT lmpDataLinkEncodingType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."OBJECT lmpDataLinkActiveOperStatus
SYNTAXINTEGER{ upAlloc(1), upFree(2), down(3)}DESCRIPTION"A value of testing(4) need not be supported."OBJECT lmpDataLinkPassiveOperStatus
SYNTAXINTEGER{ upAlloc(1), upFree(2), down(3)}DESCRIPTION"A value of psvTst(4) need not be supported."OBJECT lmpDataLinkRowStatus
SYNTAXRowStatus{ active(1)}MIN-ACCESSread-onlyDESCRIPTION"Write access is not required, and active(1) is the
only status that needs to be supported."OBJECT lmpDataLinkStorageType
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."::={ lmpCompliances 2}-- Units of conformancelmpNodeGroup OBJECT-GROUPOBJECTS{ lmpAdminStatus,
lmpOperStatus,
lmpNbrAdminStatus,
lmpNbrOperStatus,
lmpNbrRowStatus,
lmpNbrStorageType,
lmpUnprotectedNotificationsEnabled,
lmpNotificationMaxRate
}STATUScurrentDESCRIPTION"Collection of objects that represent LMP node
configuration."::={ lmpGroups 1}lmpControlChannelGroup OBJECT-GROUPOBJECTS{
lmpNbrRetransmitInterval,
lmpNbrRetryLimit,
lmpNbrRetransmitDelta,
lmpNbrAdminStatus,
lmpNbrOperStatus,
lmpNbrRowStatus,
lmpNbrStorageType,
lmpCcHelloIntervalDefault,
lmpCcHelloIntervalDefaultMin,
lmpCcHelloIntervalDefaultMax,
lmpCcHelloDeadIntervalDefault,
lmpCcHelloDeadIntervalDefaultMin,
lmpCcHelloDeadIntervalDefaultMax,
lmpCcNbrNodeId,
lmpCcRemoteId,
lmpCcRemoteAddressType,
lmpCcRemoteIpAddr,
lmpCcSetupRole,
lmpCcAuthentication,
lmpCcHelloInterval,
lmpCcHelloIntervalMin,
lmpCcHelloIntervalMax,
lmpCcHelloIntervalNegotiated,
lmpCcHelloDeadInterval,
lmpCcHelloDeadIntervalMin,
lmpCcHelloDeadIntervalMax,
lmpCcHelloDeadIntervalNegotiated,
lmpCcOperStatus,
lmpCcRowStatus,
lmpCcStorageType,
lmpCcUpDownNotificationsEnabled
}STATUScurrentDESCRIPTION"Objects that can be used to configure LMP interface."::={ lmpGroups 2}lmpCcIsInterfaceGroup OBJECT-GROUPOBJECTS{ lmpCcIsIf }STATUScurrentDESCRIPTION"Objects that can be used to configure control channels
that are interfaces."::={ lmpGroups 3}lmpCcIsNotInterfaceGroup OBJECT-GROUPOBJECTS{ lmpCcUnderlyingIfIndex,
lmpCcIsIf,
lmpCcLastChange,
lmpCcAdminStatus
}STATUScurrentDESCRIPTION"Objects that can be used to configure control channels
that are not interfaces."::={ lmpGroups 4}lmpLinkPropertyCorrelationGroup OBJECT-GROUPOBJECTS{ lmpLinkPropertyNotificationsEnabled }STATUScurrentDESCRIPTION"Collection of objects used to configure the link
property correlation procedure."::={ lmpGroups 5}lmpLinkVerificationGroup OBJECT-GROUPOBJECTS{ lmpGlobalLinkVerificationInterval,
lmpLinkVerifyInterval,
lmpLinkVerifyDeadInterval,
lmpLinkVerifyTransportMechanism,
lmpLinkVerifyAllLinks,
lmpLinkVerifyTransmissionRate,
lmpLinkVerifyWavelength,
lmpLinkVerifyRowStatus,
lmpLinkVerifyStorageType,
lmpDataLinkNotificationsEnabled
}STATUScurrentDESCRIPTION"Collection of objects that represent the link
verification procedure configuration."::={ lmpGroups 6}lmpPerfGroup OBJECT-GROUPOBJECTS{ lmpCcInOctets,
lmpCcInDiscards,
lmpCcInErrors,
lmpCcOutOctets,
lmpCcOutDiscards,
lmpCcOutErrors,
lmpCcConfigReceived,
lmpCcConfigSent,
lmpCcConfigRetransmit,
lmpCcConfigAckReceived,
lmpCcConfigAckSent,
lmpCcConfigNackSent,
lmpCcConfigNackReceived,
lmpCcHelloReceived,
lmpCcHelloSent,
lmpCcBeginVerifyReceived,
lmpCcBeginVerifySent,
lmpCcBeginVerifyRetransmit,
lmpCcBeginVerifyAckReceived,
lmpCcBeginVerifyAckSent,
lmpCcBeginVerifyNackReceived,
lmpCcBeginVerifyNackSent,
lmpCcEndVerifyReceived,
lmpCcEndVerifySent,
lmpCcEndVerifyRetransmit,
lmpCcEndVerifyAckReceived,
lmpCcEndVerifyAckSent,
lmpCcTestStatusSuccessReceived,
lmpCcTestStatusSuccessSent,
lmpCcTestStatusSuccessRetransmit,
lmpCcTestStatusFailureReceived,
lmpCcTestStatusFailureSent,
lmpCcTestStatusFailureRetransmit,
lmpCcTestStatusAckReceived,
lmpCcTestStatusAckSent,
lmpCcLinkSummaryReceived,
lmpCcLinkSummarySent,
lmpCcLinkSummaryRetransmit,
lmpCcLinkSummaryAckReceived,
lmpCcLinkSummaryAckSent,
lmpCcLinkSummaryNackReceived,
lmpCcLinkSummaryNackSent,
lmpCcChannelStatusReceived,
lmpCcChannelStatusSent,
lmpCcChannelStatusRetransmit,
lmpCcChannelStatusAckReceived,
lmpCcChannelStatusAckSent,
lmpCcChannelStatusReqReceived,
lmpCcChannelStatusReqSent,
lmpCcChannelStatusReqRetransmit,
lmpCcChannelStatusRspReceived,
lmpCcChannelStatusRspSent,
lmpCcCounterDiscontinuityTime,
lmpTeInOctets,
lmpTeOutOctets,
lmpTeBeginVerifyReceived,
lmpTeBeginVerifySent,
lmpTeBeginVerifyRetransmit,
lmpTeBeginVerifyAckReceived,
lmpTeBeginVerifyAckSent,
lmpTeBeginVerifyNackReceived,
lmpTeBeginVerifyNackSent,
lmpTeEndVerifyReceived,
lmpTeEndVerifySent,
lmpTeEndVerifyRetransmit,
lmpTeEndVerifyAckReceived,
lmpTeEndVerifyAckSent,
lmpTeTestStatusSuccessReceived,
lmpTeTestStatusSuccessSent,
lmpTeTestStatusSuccessRetransmit,
lmpTeTestStatusFailureReceived,
lmpTeTestStatusFailureSent,
lmpTeTestStatusFailureRetransmit,
lmpTeTestStatusAckReceived,
lmpTeTestStatusAckSent,
lmpTeLinkSummaryReceived,
lmpTeLinkSummarySent,
lmpTeLinkSummaryRetransmit,
lmpTeLinkSummaryAckReceived,
lmpTeLinkSummaryAckSent,
lmpTeLinkSummaryNackReceived,
lmpTeLinkSummaryNackSent,
lmpTeChannelStatusReceived,
lmpTeChannelStatusSent,
lmpTeChannelStatusRetransmit,
lmpTeChannelStatusAckReceived,
lmpTeChannelStatusAckSent,
lmpTeChannelStatusReqReceived,
lmpTeChannelStatusReqSent,
lmpTeChannelStatusReqRetransmit,
lmpTeChannelStatusRspSent,
lmpTeChannelStatusRspReceived,
lmpTeCounterDiscontinuityTime,
lmpDataLinkTestReceived,
lmpDataLinkTestSent,
lmpDataLinkActiveTestSuccess,
lmpDataLinkActiveTestFailure,
lmpDataLinkPassiveTestSuccess,
lmpDataLinkPassiveTestFailure,
lmpDataLinkDiscontinuityTime
}STATUScurrentDESCRIPTION"Collection of objects used to provide performance
information about LMP interfaces and data-bearing links."::={ lmpGroups 7}lmpTeLinkGroup OBJECT-GROUPOBJECTS{ lmpTeLinkNbrRemoteNodeId,
lmpTeLinkVerification,
lmpTeLinkFaultManagement,
lmpTeLinkDwdm,
lmpTeLinkOperStatus,
lmpTeLinkRowStatus,
lmpTeLinkStorageType,
lmpTeLinkNotificationsEnabled
}STATUScurrentDESCRIPTION"Objects that can be used to configure TE links."::={ lmpGroups 8}lmpDataLinkGroup OBJECT-GROUPOBJECTS{ lmpDataLinkType,
lmpDataLinkAddressType,
lmpDataLinkIpAddr,
lmpDataLinkRemoteIpAddress,
lmpDataLinkRemoteIfId,
lmpDataLinkEncodingType,
lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus,
lmpDataLinkRowStatus,
lmpDataLinkStorageType
}STATUScurrentDESCRIPTION"Collection of objects that represent data-bearing link
configuration."::={ lmpGroups 9}lmpNotificationGroup NOTIFICATION-GROUPNOTIFICATIONS{ lmpTeLinkPropertyMismatch,
lmpDataLinkPropertyMismatch,
lmpUnprotected,
lmpControlChannelUp,
lmpControlChannelDown,
lmpTeLinkDegraded,
lmpTeLinkNotDegraded,
lmpDataLinkVerificationFailure }STATUScurrentDESCRIPTION"Set of notifications defined in this module."::={ lmpGroups 10}-- End of LMP-MIBEND